COMMENT ⊗   VALID 00004 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002						Thursday, March 8  1979
C00004 00003	USER commands are:  [As in USR.SAI[1,IAZ]]
C00007 00004	SERVER.[As in SVR.SAI[1,IAZ]]
C00013 ENDMK
C⊗;
					Thursday, March 8  1979





	This is DLNFTP.IAZ[up,doc].The information in this file explains
how to give commands to the Dialnet File Transfer user program, and how
our server executes them. this is the current situation, which will
be updated with the programs.
	Command words may be in upper,lower or mixed case. Spaces
are not significant, except that there must be one space following the 
command word and one before the TO in the RENAME command.
	All commands can be abbreviated provided that the abbreviation are not 
ambiguous.

	An explanation of the File Transfer Protocol can be found in
ftp.pro[1,iaz].
USER commands are:  [As in USR.SAI[1,IAZ]]
		    (All command codes can be shortened upto ambiguity)
 
USER (or LOGIN)  <user-id>	........To identify yourself to the server.
PASSWORD <pasw>		........If required (type only <passw> to the prompt).
ACCOUNT <acc>		........If required (type only <acc> to the prompt).
CWP (or ALIAS) <dirname>	........To change working directory.
DATA <bytesize> <type> <structure> .....To give the parameters of the data transfer.
				Only `8 ASCII FILE' and `36 IMAGE FILE' implemented.
				`DATA I' is enough to get image mode and anything
				else (including simply `DATA') will return you to 
				ascii mode.
RENAME <fname1> TO <fname2>	........<fname2> will be the new name of
					<fname1> at the server.
DELETE <fname>      ........To delete file fname at the server.
DIRECTORY <user-id>	........To get a listing of a directory.
SERVER		     ........To obtain information about such things as Dialnet
			     commands implemented by the server, user names and
			     file naming conventions at the server site,etc..
STATUS		     ........To get whatever information the server wants
			     to give.
RETRIEVE (or GET)  <fname1> ← <fname2>	........<fname1> will get the data.
STORE (or PUT or SEND)  <fname1> → <fname2> ......<fname2> will get the data
						   sent by the user.
APPEND <fname1>→<fname2>	........<fname1> will be appended to <fname2>
					at the server.
ABORT			........To abort the previously requested data transfer.
BYE (or QUIT or KILL)	........To close the connection.
? or HELP		........To read this file.

[ This is file rpcuft.doc[net,sys] at SAIL.]
SERVER.[As in SVR.SAI[1,IAZ]]

   Our server takes project-programmer names with the formats

	  [project,programmer]  or  [project,programmer 

In USER commands, a programmer name is enough [project 1 will be assumed],
and in CWD commands a project name suffices [the current programmer name
will be assumed].
 
File names must be in one of the formats:
		name 	  or    name[ppn]
	  or    name.ext  or    name.ext[ppn]  
          or ↓name↓.↓ext↓ or   ↓name↓.↓ext↓[ppn]
thus, either the ppn is not given [and then the current working directory
is assumed] or it must start with a left bracket.
 
  It accepts all the commands described in the Dialnet Protocols, with the
following remarks:

	There are no accounts at SUAI and a simple reply to ACCOUNT is sent
without any check.
	Only `8 ASCII FILE' and `36 IMAGE FILE' transfer parameters are
implemented.
	The reply to the DIRECTORY command is a list of lists. Each sublist
contains a file name,file extension [if there is one] and file size in 36-bit
words.

[ This is file rpcsft.doc[net,sys] at SAIL.]